Clarify that Dependabot workflows bypass Actions policy checks and disablement#38421
Clarify that Dependabot workflows bypass Actions policy checks and disablement#38421
Conversation
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
Previous broken links comment now moot. 👌😙 |
There was a problem hiding this comment.
Pull Request Overview
This PR clarifies that enabling Dependabot workflows bypasses GitHub Actions policy checks and disablement, ensuring users understand that these workflows always run regardless of repository or enterprise settings.
- Adds an IMPORTANT callout to the "Automating Dependabot with GitHub Actions" page.
- Introduces a new "📌 Dependabot and GitHub Actions Policies" section explaining policy and disablement bypass.
- Updates the intro and adds an IMPORTANT callout in the "About Dependabot on GitHub Actions runners" page.
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md | Added an IMPORTANT note and a new policy section detailing how Dependabot bypasses Actions policies and disablement. |
| content/code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners.md | Updated the intro to mention bypass behavior and added an IMPORTANT callout in the "About" section. |
...ode-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
Outdated
Show resolved
Hide resolved
...ode-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
Outdated
Show resolved
Hide resolved
...ode-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
Outdated
Show resolved
Hide resolved
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Closes: https://github.com/github/docs-content/issues/14456
What's being changed (if available, include any code snippets, screenshots, or gifs):
This PR updates the documentation to clarify the behavior of Dependabot when GitHub Actions is disabled or restricted by policy checks.
Pages updated:
automating-dependabot-with-github-actions.mdabout-dependabot-on-github-actions-runners.mdKey changes:
[!IMPORTANT]note to both pages emphasizing this behavior"📌 Dependabot and GitHub Actions Policies"section to first explain normal GitHub Actions enforcement, then describe Dependabot's exceptionintro:metadata in the second doc to reflect the bypass behaviorThese updates ensure that customers understand why Dependabot workflows run even when other GitHub Actions workflows may be restricted or blocked.
Check off the following: